Re-calcaulate DLX attribute

Hello,

from what I have read this will do the trick for re-calculating the DXL values. Currently I have two questions:

1) It seems that just by switching to edit mode it forces the DXL to re-calculate or am I overlooking something.
2) When baselining do you have to re-calculate the values for the DXL attribute or will DOORS do that prior to the actually baseline commit?

Thank you,
-Jim

pragma runLim,0 
 
const string attrDXLName = "DXL for Out-links (All modules)"
 
Module m = current
if (!isEdit m) m = edit(fullName m, true, true)
if (null m){ack "Could not edit current module!";halt;}
 
string  Value
Object  obj
for obj in entire m do{Value = obj.attrDXLName}
 
downgrade(m)

SystemAdmin - Tue Aug 07 14:07:50 EDT 2012

Re: Re-calcaulate DLX attribute
llandale - Tue Aug 07 14:56:49 EDT 2012

Switching to Edit is considered "opening" the module. Read to Shared is also. I seem to rememeber that switching to Shared from Edit is also. So it seems Attr-DXL is erased after an open module.

Attr-DXL in Baselines are calculated now; not saved in the baseline. That seriously reduces the value of Attr-DXL in the baseline; where surely we'd prefer to save their actual value at the time. Guess we need a "Capture Attr-DXL" script that writes to comperable string attributes.

-Louie

Re: Re-calcaulate DLX attribute
SystemAdmin - Tue Aug 07 15:17:29 EDT 2012

llandale - Tue Aug 07 14:56:49 EDT 2012
Switching to Edit is considered "opening" the module. Read to Shared is also. I seem to rememeber that switching to Shared from Edit is also. So it seems Attr-DXL is erased after an open module.

Attr-DXL in Baselines are calculated now; not saved in the baseline. That seriously reduces the value of Attr-DXL in the baseline; where surely we'd prefer to save their actual value at the time. Guess we need a "Capture Attr-DXL" script that writes to comperable string attributes.

-Louie

Hello,

Louie stated: "Attr-DXL in Baselines are calculated now; not saved in the baseline. That seriously reduces the value of Attr-DXL in the baseline; where surely we'd prefer to save their actual value at the time. Guess we need a "Capture Attr-DXL" script that writes to comperable string attributes."

form what I can tell they get baselined. DOORS 9.3.0.7

-Jim

Re: Re-calcaulate DLX attribute
llandale - Wed Aug 08 11:10:38 EDT 2012

SystemAdmin - Tue Aug 07 15:17:29 EDT 2012
Hello,

Louie stated: "Attr-DXL in Baselines are calculated now; not saved in the baseline. That seriously reduces the value of Attr-DXL in the baseline; where surely we'd prefer to save their actual value at the time. Guess we need a "Capture Attr-DXL" script that writes to comperable string attributes."

form what I can tell they get baselined. DOORS 9.3.0.7

-Jim

The values of this attr-DXL are not preserved in the baseline, it displays the date and time when you load the baseline (..er.. the view in the baseline):

obj.attrDXLName = dateAndTime(today) ""

I wonder if your attr-DXL is following baselined links (to other baselines); in which case the value calculated now is the same as it was when it was baselined.

-Louie

Re: Re-calcaulate DLX attribute
llandale - Wed Aug 08 11:12:17 EDT 2012

llandale - Wed Aug 08 11:10:38 EDT 2012
The values of this attr-DXL are not preserved in the baseline, it displays the date and time when you load the baseline (..er.. the view in the baseline):

obj.attrDXLName = dateAndTime(today) ""

I wonder if your attr-DXL is following baselined links (to other baselines); in which case the value calculated now is the same as it was when it was baselined.

-Louie

Yes, if you baseline the module and then change the Attr-DXL code; the baseline preserves the old code. Of course. But I'm talking about the attr-DXL value; which appears is not stored in the baseline but is calculated when queried.

-Louie

Re: Re-calcaulate DLX attribute
SystemAdmin - Wed Aug 08 11:25:17 EDT 2012

llandale - Wed Aug 08 11:12:17 EDT 2012
Yes, if you baseline the module and then change the Attr-DXL code; the baseline preserves the old code. Of course. But I'm talking about the attr-DXL value; which appears is not stored in the baseline but is calculated when queried.

-Louie

Hello,

So what would happen if you had the DXLAttr write to a text attribute would your get a run-time error if the DXLAttr triggered within a baseline?

Thank you,
-Jim

Re: Re-calcaulate DLX attribute
llandale - Wed Aug 08 11:39:36 EDT 2012

SystemAdmin - Wed Aug 08 11:25:17 EDT 2012
Hello,

So what would happen if you had the DXLAttr write to a text attribute would your get a run-time error if the DXLAttr triggered within a baseline?

Thank you,
-Jim

I guess yes. But code that sets values should always check access, or trap errors anyway.

noError()
obj.NameTextAttr = whatever
lastError()

-Louie